Skip to content

Fix null parameter handling for mcpo/Open WebUI#3

Merged
KI7MT merged 1 commit into
mainfrom
fix/null-params
Mar 14, 2026
Merged

Fix null parameter handling for mcpo/Open WebUI#3
KI7MT merged 1 commit into
mainfrom
fix/null-params

Conversation

@KI7MT

@KI7MT KI7MT commented Mar 14, 2026

Copy link
Copy Markdown
Member

Summary

  • 2 params in parse_adif: start_at and limit
  • Type annotations accept None (int | None), runtime coercion converts None → defaults
  • Fixes mcpo/Pydantic rejection when llama.cpp sends null for optional params
  • Version bump: 1.0.3 → 1.0.4

Test plan

  • Test via mcpo proxy with null params (curl -X POST with null values)
  • Test via Claude Code MCP (9975WX fixture)
  • Run test_security.py
  • Verify on Newton/Open WebUI

Fixes #2

🤖 Generated with Claude Code

Type annotations changed to accept None (int | None) so mcpo/Pydantic
doesn't reject null values. Runtime coercion converts None → defaults.
2 params in parse_adif.

Fixes #2

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

@KI7MT KI7MT left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Watson Security Review: PASS

  • 6/6 security tests passing on fix/null-params branch
  • Fix pattern matches fleet standard (Type | None + runtime coercion)
  • 2 params in parse_adif verified: start_at, limit
  • No security regressions, no new dependencies
  • Version bump 1.0.3 → 1.0.4 correct

✅ Approved — Bob, merge when ready, update issues, tag + publish.

@KI7MT KI7MT merged commit 87b8792 into main Mar 14, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix null parameter handling — mcpo/Open WebUI compatibility

1 participant